home *** CD-ROM | disk | FTP | other *** search
- Path: access4.digex.net!not-for-mail
- From: ell@access4.digex.net (Ell)
- Newsgroups: comp.lang.c++
- Subject: Re: Pure Virtual Destructor Question
- Date: 10 Feb 1996 21:26:01 GMT
- Organization: The Universe
- Message-ID: <4fj2h9$f71@news4.digex.net>
- References: <4fecq0$k4e@news4.digex.net> <4fg2s5$r02@cnn.exu.ericsson.se> <4fgp0o$759@news4.digex.net> <311cc66a.2683598@news.interlog.com>
- NNTP-Posting-Host: access4.digex.net
- X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
-
- Nicholas Scott (object@interlog.com) wrote:
- : ell@access4.digex.net (Ell) writes:
- : >Immediately above you are logically "defining" your "pure virtual" :
- : >destructor "inside the class where it is "declared" as a pure virtual
- : >function. It is _illegal_ to logically, or physically "define" a pure
- : >virtual function in the class it is "declared" in. A pure virtual
- : >should
-
- : Nonsense... implementations can be supplied for pure virtuals...
- : further they can also be invoked.
-
- I belive I am correct in saying that it is illegal to define a pure
- virtual within the physical confines of the class declaring the pure
- virtual. At least that is how my compiler works, and what I understand
- from the '92 ARM, and the C++ FAQ book. However, you are correct in
- alluding to the fact that a function definition may be supplied for a pure
- virtual function for the class where the pure virtual has been declared.
- So we both win, eh? :)
-
- And even with this defintion, the class is abstract and can not be
- instantiated. Now this is the C++ I know and like. :)
-
- Elliott
-